View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001166 | T99X171.00 SKB Eagle | VOC | public | 2021-03-09 12:38 | 2021-09-30 18:47 |
| Reporter | (ALTech) Younkwang Jung | Assigned To | Due Date | ||
| Priority | urgent | Severity | s2-severe | Reproducibility | have not tried |
| Status | closed | Resolution | fixed | ||
| Summary | 0001166: [Eagle][ATV][VOC] issue that TV off immediately after the TV is on | ||||
| Description | Hi Kerwin FW : v15.522.60 When turning on STB with the integrated power button on the RCU , there is an issue that TV off immediately after the TV is on I attached the log, so please check it. Thanks YK.Jung | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(ALTech) SY Yoon |
|---|
|
|
|
|
|
Hi kerwin In the log, the I-Set command was sent to the RCU two seconds (2.2 to 2.4 seconds) after receiving the power key from the STB. 0130000013_20210309_28_CD_C4_FC_C9_01 // Power Off (sleep) 348 03-06 13:47:25.015 D 4751 4751 KeyEventManager: onKeyDown : POWER 442 03-06 13:47:25.382 D 4751 4751 KeyEventManager: onKeyUp : POWER 459 03-06 13:47:25.387 I 4751 4751 MainActivity: sleep() called 1311 03-06 13:47:25.916 E 4785 4785 iSet : Write Screen Off 1312 03-06 13:47:25.933 E 4785 4811 iSet : OnWrite 0000ffe1-0000-1000-8000-00805f9b34fb, id= 98, status= 0 // Power On (wakeup) 2658 03-06 13:47:33.593 D 4751 4751 KeyEventManager: onKeyDown : POWER 2703 03-06 13:47:34.005 D 4751 4751 KeyEventManager: onKeyUp : POWER 2713 03-06 13:47:34.009 I 4751 4751 MainActivity: wakeup() called 4245 03-06 13:47:36.130 E 4785 4785 iSet : Write Screen On 4348 03-06 13:47:36.148 E 4785 4811 iSet : OnWrite 0000ffe1-0000-1000-8000-00805f9b34fb, id= 98, status= 0 0130000013_20210309_28_CD_C4_FC_C9_7F // Power Off (sleep) 5749 03-07 15:56:29.857 D 4730 4730 KeyEventManager: onKeyDown : POWER 5841 03-07 15:56:30.121 D 4730 4730 KeyEventManager: onKeyUp : POWER 5856 03-07 15:56:30.125 I 4730 4730 MainActivity: sleep() called 6097 03-07 15:56:30.555 E 4742 4742 iSet : Write Screen Off 6098 03-07 15:56:30.575 E 4742 4807 iSet : OnWrite 0000ffe1-0000-1000-8000-00805f9b34fb, id= 98, status= 0 // Power On (wakeup) 7535 03-07 15:56:42.539 D 4730 4730 KeyEventManager: onKeyDown : POWER 7577 03-07 15:56:42.807 D 4730 4730 KeyEventManager: onKeyUp : POWER 7587 03-07 15:56:42.810 I 4730 4730 MainActivity: wakeup() called 441 03-07 15:56:45.055 E 4742 4742 iSet : Write Screen On 482 03-07 15:56:45.076 E 4742 4807 iSet : OnWrite 0000ffe1-0000-1000-8000-00805f9b34fb, id= 98, status= 0 == In RCU == If the RCU fails to receive feedback within 2 seconds of the i-set command, it will turn off the TV, judging that the TV is not connected to the STB. In conclusion, STB should send feedback to RCU within 2 seconds after receiving the power On command. You need to check this part. Thank you YK.Jung |
|
|
Reminder sent to: (SW) Kerwin Chen |
|
|
Hi Mr. Jung I can't find that iSet should send "screen on/off" command to RCU within 2 seconds in iSet spec. I reduced the delay time as much as possible. You can test the attachment iSet-15.apk (adb install -r iSet-15.apk) You can use Google Settings > apps > see all apps > iSet to check the version 15 is installed correctly. But I think the root cause is not in iSet. iSet is just an application. It is background service (No UI application), so it can not detect key code. We use broadcast-receiver to receive suspend/wake broadcast from framework and do the corresponding iSet command, so if system is busy during suspend/wake, the iSet may receive suspend/wake broadcast more slowly. |
|
|
Hi Jason I have one question My test results are too different from the field. You're saying that you've reduced the possible delay. Based on SW, how much has it improved compared to before? Thanks |
|
|
Hi Mr. Jung I removed 250ms delay. |
|
|
Hi Mr. Jason Ling, I have question why both write screen on and off time are different. And can you check normal time for spend time to write screen on and off time from the sleep() or wakeup() call ? |
|
|
Hi Mr. Yoon, it's depend on system loading. In previous version. our implementation in iSet is just waiting fixed time of 250ms when we receive system broadcast (suspend/wake), then write iSet command to RCU I can not control when the iSet can receive the broadcast. iSet is just an application. Now I can not check normal time for spending time to write screen on and off time from the sleep() or wakeup() call. Because when we press power key, the OTA dialog will pop up to affect my test. Moreover, all the processes are as follows, Step 1. when kernel level receive POWER key event, kernel will pass it to Android framework, Step 2. the Android framework will handle the key and send the broadcast. (the broadcast is implement by MW) Step 3. when iSet receive broadcast, iSet will write screen on/off command to RCU. We only handle Step3, and I remove the 250 ms delay in step 3 in iSet (version 15), Now there is no delay in iSet when iSet receive suspend/wake broadcast. I think the time for Step 2 depends on system loading, how many processes are running in the foreground/background when STB are ready to standy/normal mode. |
|
|
Hi Jason Is there any other issue if we actually apply iSet-15.apk that reduced this delay? SKB manager has requested to apply this improved iSet-15.apk. We're going to make a final FW soon. Please let me know if there are any parts that need to be checked or modified. Thanks!! |
|
|
Hi Mr. Jung, Regarding iSet, We Just removed the 250 delay when receiving suspend/wake broadcast. it's minimum modification and I have uploaded it to bitbucket. Regarding the final FW, could you check the current security patch level with other OEM vendor. our security patch level is 2021-01, I think that we should apply 2021-02 in these days. |
|
|
Hi Jason SKB manager does not want to apply the security patch(2021-02) to this release. Thanks |
|
|
Hi Mr. Jung I have uploaded the 2021-02 security patch, Now our release is controlled by manifest which release by Sptek. I think SPTEK can use manifest.xml to control which commits SKB want to include in next release. If they can not do it, we will revert it. For SW release plan, If the final FW can not be tested by 3PL within this March. I think that we MUST apply 2021-02 Security patch. Please evaluate the BMT time and Self Pretest time and 3PL test time. If we don't apply 2021-02 at this moment, please let us know when we should apply it? |
|
|
Hi Jason Please don't apply 2021-02 security patch . I will talk to the SKB manager about when it will be applied. Thank |
|
|
Hi Mr. Jung, This case has been fix in iSet (version 15) |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-03-09 12:38 | (ALTech) Younkwang Jung | New Issue | |
| 2021-03-09 12:38 | (ALTech) Younkwang Jung | Status | new => assigned |
| 2021-03-09 12:38 | (ALTech) Younkwang Jung | Assigned To | => (SW) Kerwin Chen |
| 2021-03-09 12:38 | (ALTech) Younkwang Jung | File Added: 0130000013_20210309_28_CD_C4_FC_C9_7F.zip | |
| 2021-03-09 12:38 | (ALTech) Younkwang Jung | File Added: 0130000013_20210309_28_CD_C4_FC_C9_01.zip | |
| 2021-03-09 12:39 | (ALTech) Younkwang Jung | Issue Monitored: (ALTech) SY Yoon | |
| 2021-03-09 15:06 | (ALTech) Younkwang Jung | Note Added: 0006272 | |
| 2021-03-10 10:58 | (ALTech) Younkwang Jung | Note Added: 0006277 | |
| 2021-03-10 11:01 | (SW) Kerwin Chen | Assigned To | (SW) Kerwin Chen => (SW) Jason Ling |
| 2021-03-10 16:43 |
|
File Added: iSet-15.apk | |
| 2021-03-10 16:43 |
|
Note Added: 0006290 | |
| 2021-03-10 16:45 |
|
Note Edited: 0006290 | |
| 2021-03-10 17:55 | (ALTech) Younkwang Jung | Note Added: 0006291 | |
| 2021-03-10 18:08 |
|
Note Added: 0006292 | |
| 2021-03-10 18:10 |
|
Note Edited: 0006290 | |
| 2021-03-10 19:05 | (ALTech) SY Yoon | Note Added: 0006293 | |
| 2021-03-10 19:37 |
|
Note Added: 0006294 | |
| 2021-03-10 19:38 |
|
Note Edited: 0006294 | |
| 2021-03-10 19:41 |
|
Note Edited: 0006294 | |
| 2021-03-11 11:03 | (ALTech) Younkwang Jung | Note Added: 0006307 | |
| 2021-03-11 11:19 |
|
Note Added: 0006309 | |
| 2021-03-12 09:48 | (ALTech) Younkwang Jung | Note Added: 0006325 | |
| 2021-03-12 10:48 |
|
Note Added: 0006327 | |
| 2021-03-12 11:57 | (ALTech) Younkwang Jung | Note Added: 0006328 | |
| 2021-04-08 15:08 |
|
Status | assigned => resolved |
| 2021-04-08 15:08 |
|
Resolution | open => fixed |
| 2021-04-08 15:08 |
|
Description Updated | View Revisions |
| 2021-04-08 15:08 |
|
Note Added: 0006635 | |
| 2021-09-30 18:47 | (ALTech) Younkwang Jung | Status | resolved => closed |
